|
|
|
|
|
|
|
In Week 2, you learn how to build objects that test themselves. That is, you create objects that have methods that test their own preconditions, including making sure that the data or class type of an incoming parameter is of the type expected. Next you delve deeply into the process of breaking up a proposed application into subsystems, including components. You learn how to identify and use design patterns for subsystems and their interactions. |
|
|
|
|
|
|
|
|
Toward the middle of the week, you learn the art of refining use cases as application and subsystem architecture blueprints. You learn about revisiting use cases in your environment, the problem statement, and the use case model. You also learn specifically how to incorporate in the design models new discoveries in the way the end user uses your VB application. |
|
|
|
|
|
|
|
|
Later in the week, you learn more about the subsystems making up the real-world example. You study the basics of the Graphical User Interface Subsystem, learning how to use the modeling techniques for GUIs and understanding the encapsulation of data presentation into a separate class. Then you implement a Graphical User Interface Subsystem by placing the core logic you generally insert in forms into classes that control the interaction between the forms and the rest of the application. |
|
|
|
|
|
|
|
|
Toward the end of the week, the Workgroup and User Security Subsystem is presented to you. This critical subsystem shows how to implement related security issues, including a class for encrypting the password. Then you wrap up the week by learning the concept of the Internal Application Manager as a mechanism for managing the states an application goes through during a typical session. |
|
|
|
|
|